Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate Jetpack helper and some parts of WPCOM helper #1149

Merged
merged 3 commits into from May 18, 2018

Conversation

gravityrail
Copy link
Contributor

@gravityrail gravityrail commented May 15, 2018

Fixes #1021

Removes the Jetpack helper after Jetpack version 6.2. Also moves some wpcom-helper functions over to Jetpack, where appropriate.

Once Automattic/jetpack#9458 is merged, this can be merged too, as AMP support will be explicitly included in Jetpack.

@westonruter
Copy link
Member

This is part of #1021

@gravityrail gravityrail changed the title Deprecate Jetpack helper Deprecate Jetpack helper and some parts of WPCOM helper May 15, 2018
@gravityrail gravityrail self-assigned this May 15, 2018
Copy link

@ebinnion ebinnion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left a few minor comments on your Jetpack PR, but things seemed to test well.

@westonruter westonruter added this to the v1.0 milestone May 18, 2018
@westonruter westonruter merged commit 927b07c into develop May 18, 2018
@westonruter westonruter deleted the try/deprecate-jetpack-helper branch May 18, 2018 19:51
@westonruter
Copy link
Member

@gravityrail I just realized that we may have a timing issue with this PR and Jetpack. If AMP 1.0 is released after Jetpack 6.2, is that going to cause a problem? If so, we may want to merge these commits into the 0.7 branch to ensure that it is released before Jetpack.

@westonruter westonruter modified the milestones: v1.0, v0.7.1 May 23, 2018
@westonruter
Copy link
Member

I've cherry-picked the commits in this branch to 0.7.1: #1170

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants